docs: Document jest's transformIgnorePatterns option to avoid pitfall
#3523
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to transpileDependencies docs
in cli-plugin-jest README
with default value. Allows easier customisation when exceptions have to be added.
LinusBorg
force-pushed
the
LinusBorg-patch-jest-transpile-docs
branch
from
dceb8ce to
826d1ff
Compare
LinusBorg
changed the title
tranformIgnorePatters option to avoid pitfalltranformIgnorePatterns option to avoid pitfall
LinusBorg
changed the title
tranformIgnorePatterns option to avoid pitfalltransformIgnorePatterns option to avoid pitfall
kazupon
approved these changes
Feb 27, 2019
|
Don't merge yet. Will undo the unnecessary formatting changes that my editor did. |
|
Should be good now. Jeeeeez.... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found that many people have issues running tests with jest, receiving an error like
"unexpected token "import".The most common reason - as far as I can tell - are packages in their node_modules that contain untranspiled ES6 imports.
While we offer the
transpileDependenciesoption, jest doesn't respect it, and rightfully so, since the issues solved by that option are often different ones (transpiling for browser compatibility).Instead, people have to adjust jest's
transformIgnorePattersoption when one of the packages they use has to be transformed bybabel-jestorvue-jest.